Skip to content

Hostname

tullamoredew.com

Last fetched

tullamoredew.com resolves to 34.248.146.14, announced in 34.248.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. tullamoredew.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 · tullamoredew.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.8/10canon.whisper.security/host/tullamoredew.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:470
Registrant organisation
domain admin
Contact emails
tullamoredew.com+registrant@customer.demys.com, gtld@demys.com, tullamoredew.com-registrant@anonymised.email

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

  • ns0.demysdns.net
  • ns1.demysdns.net
  • ns2.demysdns.net
  • ns3.demysdns.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
  • ns4.demysdns.co.uk
  • ns5.demysdns.co.uk
  • ns6.demysdns.co.uk

MX records

  • cust3131-1.in.mailcontrol.com
  • cust3131-2.in.mailcontrol.com
  • cust3131-3.in.mailcontrol.com
  • cust3131-4.in.mailcontrol.com
  • tullamoredew-com.mail.protection.outlook.com

SPF policy

  • ip: 109.68.65.35/32
  • ip: 162.13.22.41/32
  • include: mailcontrol.com
  • include: spf.protection.outlook.com
  • a: tullamoredew.com
  • mx: tullamoredew.com

Threat-feed evidence

History

Related pages

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