Skip to content

Hostname

datacontact.hu

Last fetched

datacontact.hu resolves to 195.228.75.149, announced in 195.228.75.0/24 by MAGYAR-TELEKOM-MAIN-AS - Magyar Telekom Plc. in HU. datacontact.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 · datacontact.huRouting diversity1.5/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/datacontact.hu

Resolution chain

IPv6 resolution

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

Attribution

magyar telekom

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for datacontact.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

Mail and authentication

Nameservers

  • dcns.integritywatch.com
  • ns1.datacontact.dc.hu
  • ns2.datacontact.dc.hu
  • ns3.datacontact.dc.hu
  • ns4.datacontact.dc.hu
  • oshf.etl.hu
  • 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

  • dc.crysys.hit.bme.hu
  • eternal.datacontact.hu
  • mail.datacontact.hu

SPF policy

  • a: jupiter.acenet.hu
  • include: crysys.hit.bme.hu
  • a: datacontact.hu
  • mx: datacontact.hu
  • a: home.etl.hu
  • a: boldi.dyndns.prj.hu
  • ip: 152.66.249.135
  • ip: 195.228.140.150
  • ip: 195.70.36.168

Threat-feed evidence

History

Related pages

Pivot from datacontact.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: "datacontact.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.