feedburner.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of feedburner.com
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
DNS Records
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 |
|---|---|---|
| www.feedburner.com | 2026-07-24 01:23:56.983 | |
| feeds.feedburner.com | 2026-07-28 17:34:09.807 | |
| feedburner.com | 2026-07-26 16:39:34.901 | |
| feeds2.feedburner.com | 2026-07-27 14:29:14.964 |
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
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.
| Origin IP | Origin ASN | CDN ASN | Confidence | Reasoning |
|---|---|---|---|---|
| 132.145.114.136 | AS31898 | AS15169 | 95% | cert 3e37d509… served by 132.145.114.136 (AS31898) carries SAN feedburner.com which currently resolves through Google (AS15169) at 142.251.13.113, 2a00:1450:4001:c25::66, 2a00:1450:4001:c25::65, 2a00:1450:4001:c25::8b |
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.