Skip to content

Hostname

molmove.hu

Last fetched

molmove.hu resolves to 20.4.131.85, announced in 20.0.0.0/11 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in NL. molmove.hu is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · molmove.huRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/molmove.hu

Resolution chain

IPv6 resolution

No AAAA record for molmove.hu is recorded in WhisperGraph.

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for molmove.hu. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
archiv.molmove.hu
freshcorner-jatek.molmove.hu
jatek.molmove.hu
pwgapp.molmove.hu
pwgapp2.molmove.hu
www.molmove.hu

Showing 6 of 10. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • ns1-35.azure-dns.com
  • ns4-35.azure-dns.info
  • ns2-35.azure-dns.net
  • ns3-35.azure-dns.org

MX records

  • alt1.emea.email.fireeyecloud.com
  • alt2.emea.email.fireeyecloud.com
  • alt3.emea.email.fireeyecloud.com
  • primary.emea.email.fireeyecloud.com

SPF policy

  • ip: 171.31.0.121/32
  • ip: 185.51.65.235/32
  • include: _spf.fireeyecloud.com
  • include: spf.protection.outlook.com
  • a: molmove.hu
  • mx: molmove.hu

Threat-feed evidence

History

Related pages

Pivot from molmove.hu 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: "molmove.hu"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.