Domain

aifa007.com

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

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of aifa007.com

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

18.172.112.21, 18.172.112.24, 18.172.112.32, 18.172.112.53

AAAA

2600:9000:2090:3600:3:d1bf:f480:93a1, 2600:9000:2090:4400:3:d1bf:f480:93a1, 2600:9000:2090:600:3:d1bf:f480:93a1, 2600:9000:2090:6e00:3:d1bf:f480:93a1, 2600:9000:2090:ac00:3:d1bf:f480:93a1, 2600:9000:2090:b600:3:d1bf:f480:93a1, 2600:9000:2090:bc00:3:d1bf:f480:93a1, 2600:9000:2090:e00:3:d1bf:f480:93a1

—

cartman.ns.cloudflare.com, tori.ns.cloudflare.com

TXT

—

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

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain	Resolves to	Last seen
aifa007.com	18.172.112.24 2600:9000:2090:b600:3:d1bf:f480:93a1 2600:9000:2090:6e00:3:d1bf:f480:93a1 2600:9000:2090:ac00:3:d1bf:f480:93a1 +8	2026-06-15 21:21:16.960

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.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

07b1f95a91e6ef53… google · argon2026h2

Subject: aifa007.com

Issuer: Amazon RSA 2048 M04

SANs: aifa007.com, *.aifa007.com