Skip to content

Hostname

isaydata.com

Last fetched

isaydata.com resolves to 83.136.252.107, announced in 83.136.248.0/21 by UPCLOUD - UpCloud Ltd in GB. isaydata.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 · isaydata.comRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/isaydata.com

Resolution chain

IPv6 resolution

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

Attribution

upcloud

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
david di tivoli
Contact emails
ironico@gmail.com, 93e8ce8eae09424a84aa1365c89bbaf0.protect@whoisguard.com, 8f96d085e96c40b2a279fcc3318a4b7f.protect@withheldforprivacy.com

Subdomains

Subdomain
www.isaydata.com

Showing 1 of 1 subdomain (1 per page).

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

  • ns11.cloudns.net
  • ns12.cloudns.net
  • ns13.cloudns.net
  • ns14.cloudns.net
  • pns11.cloudns.net
  • pns12.cloudns.net
  • pns13.cloudns.net
  • pns14.cloudns.net
  • 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

  • isaydata.com

Threat-feed evidence

History

Related pages

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