Hostname
tidesports.com
Last fetched
tidesports.com resolves to 146.75.118.62, announced in 146.75.116.0/22 by FASTLY - Fastly, Inc. in DE. tidesports.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
- 146.75.118.62
146.75.116.0/22 · FASTLY - Fastly, Inc. · Frankfurt am Main, DE
- 146.75.122.62
146.75.120.0/22 · FASTLY - Fastly, Inc. · Frankfurt am Main, DE
- 146.75.38.62
146.75.36.0/22 · FASTLY - Fastly, Inc. · Ashburn, US
- 151.101.158.62
151.101.156.0/22 · FASTLY - Fastly, Inc. · Chennai, IN
- 151.101.190.62
151.101.188.0/22 · FASTLY - Fastly, Inc. · Amsterdam, NL
- 151.101.62.62
151.101.60.0/22 · FASTLY - Fastly, Inc. · London, GB
- 199.232.58.62
199.232.56.0/22 · FASTLY - Fastly, Inc. · London, GB
- 140.248.134.62
140.248.132.0/22 · FASTLY - Fastly, Inc. · Denver, US
IPv6 resolution
No AAAA record for tidesports.com is recorded in WhisperGraph.
Attribution
Fastly
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:3786
- Registrant organisation
- gannett media
- Contact emails
- anonymous-registrant@brandsight.com, domains@halifaxmediagroup.com, domains@nytrng.com
Subdomains
Showing 3 of 3 subdomains (3 per page).
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
- ns01.gannett-dns.com
- ns02.gannett-dns.com
- ns03.gannett-dns.com
- ns04.gannett-dns.com
- dns1.p01.nsone.net
- dns2.p01.nsone.net
- dns3.p01.nsone.net
- dns4.p01.nsone.net
- dns1.p05.nsone.net
- dns2.p05.nsone.net
- dns3.p05.nsone.net
- dns4.p05.nsone.net
MX records
- tidesports-com.mail.protection.outlook.com
SPF policy
- include: cust-spf.exacttarget.com
- include: spf.gannett.com
Threat-feed evidence
History
Related pages
Pivot from tidesports.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: "tidesports.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.