Domain

ca.gov

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

DNS Check HTTP Check Run Full Scan .gov TLD

Run a live full scan of ca.gov

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now

Hosting IPs

—

A/AAAA targets

Subdomains

—

CT + scan + body

Record Types

—

seen in DNS

Observed Certs

—

in our scans

DNS Records

150.171.109.100, 150.171.109.101, 150.171.109.183, 150.171.109.193, 150.171.109.33, 150.171.109.34, 150.171.109.35, 150.171.109.36

AAAA

2603:1061:14:135::1, 2603:1061:14:174::1, 2603:1061:14:20::1, 2603:1061:14:21::1, 2603:1061:14:22::1, 2603:1061:14:23::1, 2603:1061:14:63::1, 2603:1061:14:64::1

50 state-ca-gov.mail.protection.outlook.com

asa.ns.cloudflare.com, chase.ns.cloudflare.com

TXT

77fek9plf3e7i9vm9i500vm79s, 7l325lj420cvll7ynrqf9sw8w0wd5rjp, 82fgh9e11st6ge8dl2rq79oc7i, 8dl8gsrz2v7brrn7v7kd8zzh5hpx3z4p, MS=ms59950388, b7jiemf9q2qic0t9aeacpttms2, facebook-domain-verification=vfdn4y9d67uzhc1fkevfdw6vc8yxmk, gdji41f1cacv1m2d198if0vuli

CNAME

—

CAA

—

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.