Hostname
link.goodevent.com
Last fetched
link.goodevent.com resolves to 104.21.23.179, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. link.goodevent.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.23.179
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.212.118
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 18.224.219.179
18.224.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.20.194.73
3.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.20.87.51
3.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.220.122.174
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.231.179.208
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.158.174.185
54.156.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for link.goodevent.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for link.goodevent.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns10.dnsmadeeasy.com
- ns11.dnsmadeeasy.com
- ns12.dnsmadeeasy.com
- ns13.dnsmadeeasy.com
- ns14.dnsmadeeasy.com
- ns15.dnsmadeeasy.com
MX records
- mx.sendgrid.net
- mx2.sendgrid.net
SPF policy
- ip: 159.183.0.0/16
- ip: 149.72.0.0/16
- ip: 168.245.0.0/17
- ip: 167.89.0.0/17
- ip: 50.31.32.0/19
- ip: 134.128.64.0/19
- ip: 134.128.96.0/19
- ip: 192.254.112.0/20
- ip: 198.37.144.0/20
- ip: 208.117.48.0/20
- ip: 198.21.0.0/21
- include: ab.sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from link.goodevent.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: "link.goodevent.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.