Skip to content

Hostname

irisndt.com

Last fetched

irisndt.com resolves to 208.109.34.188, announced in 208.109.32.0/21 by GO-DADDY-COM-LLC - GoDaddy.com, LLC in US. irisndt.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 · irisndt.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/irisndt.com

Resolution chain

IPv6 resolution

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

Attribution

godaddy com

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
irisndt
Contact emails
isusprocurement@irisndt.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

  • ns1-06.azure-dns.com
  • ns4-06.azure-dns.info
  • ns2-06.azure-dns.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
  • ns3-06.azure-dns.org

MX records

  • irisndt-com.mail.protection.outlook.com

SPF policy

  • include: spf-westus.emailsignatures365.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • ip: 107.0.107.186
  • ip: 144.130.167.226
  • ip: 188.39.224.122
  • ip: 20.109.156.250
  • ip: 208.109.34.188
  • ip: 209.115.155.34
  • ip: 209.115.155.41
  • ip: 209.91.94.138
  • ip: 209.91.94.157
  • ip: 209.91.94.170
  • ip: 49.196.253.223
  • ip: 50.207.139.200
  • ip: 50.222.98.162
  • ip: 78.32.251.141
  • ip: 78.32.251.157

Threat-feed evidence

History

Related pages

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