Hostname
mondinion.com
Last fetched
mondinion.com resolves to 38.68.134.186, announced in 38.68.134.0/24 by AS-GLOBALTELEHOST - GTHost in US. mondinion.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
- 38.68.134.186
38.68.134.0/24 · AS-GLOBALTELEHOST - GTHost · Dallas, US
- 38.68.135.120
38.68.135.0/24 · AS-GLOBALTELEHOST - GTHost · Trumbull, US
IPv6 resolution
No AAAA record for mondinion.com is recorded in WhisperGraph.
Attribution
gthost
ORIGIN_AS
WHOIS identity
- Registrar
- iana:48
- Registrant organisation
- premier world ltd. zoltan baranyai ()
- Contact emails
- office@premierworld.biz
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- linda.ns.cloudflare.com
- marek.ns.cloudflare.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
MX records
- mail.mondinion.com
SPF policy
- a: mondinion.com
- mx: mondinion.com
- a: vps1.mondinion.com
- a: vps10.mondinion.com
- a: vps11.mondinion.com
- a: vps12.mondinion.com
- a: vps13.mondinion.com
- a: vps14.mondinion.com
- a: vps15.mondinion.com
- a: vps2.mondinion.com
- a: vps3.mondinion.com
- a: vps4.mondinion.com
- a: vps5.mondinion.com
- a: vps6.mondinion.com
- a: vps7.mondinion.com
- a: vps8.mondinion.com
- a: vps9.mondinion.com
- ip: 173.255.193.136
- ip: 23.142.26.176
- ip: 2600:3c00:0:0:f03c:91ff:fe8b:c8f8
- ip: 38.121.43.116
- ip: 38.68.134.186
- ip: 38.68.135.120
- ip: 82.78.103.210
Threat-feed evidence
History
Related pages
Pivot from mondinion.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: "mondinion.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.