Hostname
nexogy.com
Last fetched
nexogy.com resolves to 74.124.215.39, announced in 74.124.212.0/22 by INMOTION - InMotion Hosting, Inc. in US. nexogy.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
- 74.124.215.39
74.124.212.0/22 · INMOTION - InMotion Hosting, Inc. · Los Angeles, US
IPv6 resolution
No AAAA record for nexogy.com is recorded in WhisperGraph.
Attribution
inmotion
ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- contact privacy inc. customer 1245610993
- Contact emails
- 3fe62e5b0a16123326319e5b1cea2d38@domaindiscreet.com, 5b890e660a28fd0a357d84cd1b0fe5bc@domaindiscreet.com, 5c4752430a28fd0a776c84bdc94e84c5@domaindiscreet.com, 5f6ca3ed0a28fd0a65076fbcc81b2dcd@domaindiscreet.com, 7f9643200a28fd0a736338c8611764aa@domaindiscreet.com, 7ul2dfbkbujgmalrn85qtam0g4@domaindiscreet.com, 8375368e0a28fd0a7ee4acd938b0ae9b@domaindiscreet.com, ab295cd90a28fd0a09d9347d6b981ba2@domaindiscreet.com, b243353b0a28fd0a1394047893d39ef1@domaindiscreet.com, dda15ba90a28fd0a4b7d41eb8a12a7b7@domaindiscreet.com, fe042e7d0a28fd0a4f734944bffa8a46@domaindiscreet.com, bm3ujrqd6sl1@contactprivacy.email
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
- ns-503.awsdns-62.com
- ns-615.awsdns-12.net
- ns-1483.awsdns-57.org
- ns-1538.awsdns-00.co.uk
MX records
- nexogy-com.mail.protection.outlook.com
SPF policy
- ip: 207.7.100.0/24
- ip: 208.65.92.0/24
- ip: 68.68.193.16/28
- include: emsd1.com
- include: spf.mandrillapp.com
- include: spf.protection.outlook.com
- include: zcsend.net
- include: mailgun.org
- ip: 63.247.150.10
- ip: 66.171.147.132
- ip: 66.171.147.142
Threat-feed evidence
History
Related pages
Pivot from nexogy.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: "nexogy.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.