Domain

p.sda1.dev

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

DNS Check HTTP Check Run Full Scan .dev TLD

Run a live full scan of p.sda1.dev

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

—

AAAA

—

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

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

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

97.64.28.79:443 href · ×34

38.127.35.158:443 href · ×32

38.127.43.94:443 href · ×32

38.127.37.149:443 href · ×32

38.127.43.226:443 href · ×32

38.127.43.212:443 href · ×31

38.127.43.71:443 href · ×31

38.127.37.186:443 href · ×31

38.127.43.74:443 href · ×31

38.127.43.205:443 href · ×31

38.127.35.190:443 href · ×31

38.127.43.236:443 href · ×31

107.163.186.245:443 href · ×20

38.127.35.175:443 href · ×16

38.127.43.224:443 href · ×16

38.127.43.86:443 href · ×16

38.127.35.159:443 href · ×16

38.127.43.99:443 href · ×16

38.127.35.144:443 href · ×16

38.127.43.125:443 href · ×16

38.127.35.183:443 href · ×16

38.127.43.96:443 href · ×16

38.127.43.73:443 href · ×16

38.127.43.240:443 href · ×16

38.127.43.109:443 href · ×16

38.127.37.184:443 href · ×16

38.127.35.149:443 href · ×16

38.127.43.66:443 href · ×16

38.127.43.248:443 href · ×16

38.127.43.118:443 href · ×16

38.127.35.155:443 href · ×16

38.127.37.168:443 href · ×16

38.127.43.81:443 href · ×16

38.127.43.223:443 href · ×16

38.127.37.176:443 href · ×16

38.127.37.173:443 href · ×16

38.127.43.204:443 href · ×16

38.127.35.163:443 href · ×16

38.127.43.80:443 href · ×16

38.127.37.163:443 href · ×16

38.127.35.135:443 href · ×16

38.127.37.132:443 href · ×16

38.127.43.195:443 href · ×16

38.127.43.222:443 href · ×16

38.127.35.132:443 href · ×16

38.127.43.116:443 href · ×16

38.127.43.124:443 href · ×16

38.127.43.201:443 href · ×16

38.127.43.253:443 href · ×16

38.127.43.111:443 href · ×16

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.