feedly.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of feedly.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 |
|---|---|---|
| feedly.com | 2026-07-28 16:28:19.762 | |
| ahead.feedly.com | 2026-06-19 21:42:01.403 | |
| blog.feedly.com | 2026-06-20 10:12:42.304 | |
| cloud.feedly.com | 2026-07-27 23:29:17.840 | |
| design.feedly.com | 2026-07-22 00:33:59.728 | |
| s2.feedly.com | 2026-07-25 09:34:36.173 | |
| s3.feedly.com | 2026-07-27 07:45:59.500 | |
| www.feedly.com | 2026-07-17 14:11:29.972 | |
| apollo.feedly.com | 1970-01-01 00:00:00.000 | |
| status.feedly.com | 2026-07-25 06:06:04.591 |
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
IPs Citing This Domain
Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.
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.
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.