Hostname
magicpin.com
Last fetched
magicpin.com resolves to 104.20.19.221, announced in 104.20.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. magicpin.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.20.19.221
104.20.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.168.249
172.66.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of magicpin.com owner
- Contact emails
- 1f41e505-4940-4e7c-b177-49353044df23@identity-protect.org, 2ab5cd66-73e9-42d8-b6e4-612929520013@identity-protect.org, a3a7059a-22dc-4324-be72-80dd52074673@identity-protect.org, a6fe0b34-46f6-463f-be6e-df788b5b8ad7@identity-protect.org, af006640-78c1-4551-8cea-3f19233788e7@identity-protect.org, cff4556b-5961-4a92-99de-d12a1aa508af@identity-protect.org, contact@privacyprotect.org, e6f29462-477e-424e-b067-d6a2557259b7@identity-protect.org, owner-4440679@magicpin.com.whoisprivacyservice.org, owner-8554836@magicpin.com.whoisprivacyservice.org, d3a7538357fc33df1c781676081b10a7d60bb52caa13597097a1acbff4576709@magicpin.com.whoisproxy.org
Subdomains
Mail and authentication
Nameservers
- david.ns.cloudflare.com
- maleah.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: amazonses.com
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from magicpin.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: "magicpin.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.