Hostname
nortonsafesearch.com
Last fetched
nortonsafesearch.com resolves to 23.99.92.83, announced in 23.96.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. nortonsafesearch.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
- 23.99.92.83
23.96.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · San Jose, US
- 40.69.201.11
40.68.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Dublin, IE
- 172.184.172.140
172.160.0.0/11 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · San Jose, US
- 20.223.132.252
20.192.0.0/10 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Dublin, IE
IPv6 resolution
No AAAA record for nortonsafesearch.com is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- domain manager
- Contact emails
- domains@symantec.com
Subdomains
| Subdomain |
|---|
| search.nortonsafesearch.com |
Showing 1 of 2. View all subdomains →
Mail and authentication
Nameservers
- edns109.ultradns.biz
- edns109.ultradns.com
- pdns5.ultradns.info
- 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
- edns109.ultradns.net
- pdns1.ultradns.net
- pdns2.ultradns.net
- udns1.ultradns.net
- udns2.ultradns.net
- edns109.ultradns.org
- pdns3.ultradns.org
- pdns4.ultradns.org
- pdns6.ultradns.co.uk
MX records
- tus1smtinbpex01.symantec.com
- tus1smtinbpex02.symantec.com
- tus1smtinbpex03.symantec.com
SPF policy
- include: %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email
Threat-feed evidence
History
Related pages
Pivot from nortonsafesearch.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: "nortonsafesearch.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.