Hostname
jjwws.com
Last fetched
jjwws.com resolves to 20.140.48.70, announced in 20.140.0.0/15 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. jjwws.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
- 20.140.48.70
20.140.0.0/15 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Phoenix, US
- 20.141.12.34
20.140.0.0/15 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Phoenix, US
- 52.235.253.123
52.224.0.0/11 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Boydton, US
- 52.244.239.112
52.224.0.0/11 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Phoenix, US
IPv6 resolution
No AAAA record for jjwws.com is recorded in WhisperGraph.
Attribution
Microsoft
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- j&j worldwide services
- Contact emails
- jsmedley@jjwws.com
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
- ns1-08.azure-dns.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
- ns1-08.azuregov-dns.us
- ns2-08.azuregov-dns.us
- ns3-08.azuregov-dns.us
- ns4-08.azuregov-dns.us
MX records
- jjwwsgov.mail.protection.office365.us
SPF policy
- ip: 40.103.0.0/16
- ip: 23.103.224.0/19
- ip: 206.191.224.0/19
- include: spf.protection.outlook.com
- include: spf.protection.office365.us
- ip: 12.5.146.207
- ip: 173.226.190.171
- ip: 173.227.74.92
- ip: 71.222.91.92
- ip: 97.105.127.138
Threat-feed evidence
History
Related pages
Pivot from jjwws.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: "jjwws.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.