Domain

www.wired.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 www.wired.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

104.18.2.159, 104.18.3.159

AAAA

2606:4700::6812:29f, 2606:4700::6812:39f

—

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.

160.251.182.198:443 href · ×29

192.241.134.186:80 href · ×20

45.55.188.13:443 href · ×19

110.42.230.2:8080 href · ×10

44.199.99.192:443 href · ×10

104.234.231.228:443 href · ×8

8.162.27.40:80 href · ×6

178.62.124.33:443 href · ×6

46.23.94.98:443 href · ×6

39.106.166.155:80 href · ×6

34.41.2.144:443 href · ×4

65.21.148.202:443 href · ×4

208.86.8.56:443 href · ×4

165.232.146.50:80 href · ×4

143.244.210.181:443 href · ×3

51.81.209.131:443 href · ×3

43.204.199.0:443 href · ×3

107.170.108.28:443 href · ×3

34.234.166.148:443 href · ×3

45.79.174.116:443 href · ×2

216.92.186.170:80 href · ×2

96.49.240.220:80 href · ×2

44.211.205.194:80 href · ×2

50.126.77.74:80 href · ×2

66.39.38.224:80 href · ×2

35.176.55.48:443 href · ×2

45.58.32.215:80 href · ×2

71.19.145.246:443 href · ×2

66.39.27.12:80 href · ×2

91.223.169.31:443 href · ×2

155.138.236.162:443 href · ×2

45.79.155.39:443 href · ×2

3.10.1.94:443 href · ×2

35.202.75.153:80 href · ×2

223.130.139.50:443 href · ×2

13.135.31.129:443 href · ×2

216.146.213.1:80 href · ×2

167.99.39.17:443 href · ×2

2.26.229.136:443 href · ×2

18.130.103.63:443 href · ×2

173.231.200.46:443 href · ×1

54.148.12.48:80 href · ×1

46.225.189.4:443 href · ×1

34.59.221.71:8443 href · ×1

45.63.68.240:443 href · ×1

51.91.248.68:443 href · ×1

142.93.126.96:443 href · ×1

35.212.185.133:443 href · ×1

199.96.128.143:80 href · ×1

158.247.242.77:80 href · ×1

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

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type	Value	First seen	Last seen
AAAA	2606:4700::6812:39f	2026-05-25 23:59:40.866	2026-07-28 20:05:38.639
AAAA	2606:4700::6812:29f	2026-05-25 23:59:40.866	2026-07-28 20:05:38.639
A	104.18.2.159	2026-05-25 23:59:40.866	2026-07-28 20:05:38.639
A	104.18.3.159	2026-05-25 23:59:40.866	2026-07-28 20:05:38.639