Skip to content

Hostname

dataeq.com

Last fetched

dataeq.com resolves to 199.60.103.165, announced in 199.60.103.0/24 by CLOUDFLARESPECTRUM - Cloudflare London, LLC in US. dataeq.com 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 · dataeq.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/dataeq.com

Resolution chain

IPv6 resolution

No AAAA record for dataeq.com is recorded in WhisperGraph.

Attribution

cloudflare london

ORIGIN_AS

WHOIS identity

Registrar
iana:69
Contact emails
dataeq.com@contactprivacy.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

  • ns-cloud-b1.googledomains.com
  • ns-cloud-b2.googledomains.com
  • ns-cloud-b3.googledomains.com
  • ns-cloud-b4.googledomains.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 167.89.41.201/32
  • include: _spf-uat.brandseye.com
  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: 25676464.spf10.hubspotemail.net
  • ip: 116.202.132.96
  • ip: 116.202.161.223
  • ip: 116.202.169.83
  • ip: 144.76.41.148
  • ip: 148.251.91.216
  • ip: 157.90.1.165
  • ip: 157.90.129.88
  • ip: 157.90.199.91
  • ip: 162.55.241.48
  • ip: 162.55.86.247
  • ip: 176.9.35.141
  • ip: 195.201.80.53
  • ip: 23.88.68.52
  • ip: 65.21.121.254
  • ip: 65.21.79.158
  • ip: 88.198.17.229
  • ip: 88.99.96.77
  • ip: 95.217.56.177
  • ip: 95.217.64.194

Threat-feed evidence

History

Related pages

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

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