Hostname
playshakespeare.com
Last fetched
playshakespeare.com resolves to 104.21.18.187, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. playshakespeare.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.18.187
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.183.33
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 69.48.180.100
69.48.176.0/21 · A2HOSTING - A2 Hosting, Inc. · Detroit, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1861
- Registrant organisation
- contact privacy inc. customer 124102871
- Contact emails
- dhxdjxzbnn7i@contactprivacy.email, 4a2dad1f724fc83890873f30f6ae3004ef90cbda140e440ff9c778103b3de1db@playshakespeare.com.whoisproxy.org, da6cf399cfbc0760c9dc285523ce65f891c8a5390283b41fb8edaa9feba0187c@playshakespeare.com.whoisproxy.org
Subdomains
Showing 12 of 53. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- albert.ns.cloudflare.com
- olivia.ns.cloudflare.com
- curitiba.ns.porkbun.com
- fortaleza.ns.porkbun.com
- maceio.ns.porkbun.com
- salvador.ns.porkbun.com
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- ip: 23.83.0.1/16
- include: _spf.google.com
- a: aspmx.l.google.com
- a: playshakespeare.com
- mx: playshakespeare.com
- a: server.playshakespeare.com
- ip: 69.48.180.100
Threat-feed evidence
History
Related pages
Pivot from playshakespeare.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "playshakespeare.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.