Skip to content

Hostname

dredmor.com

Last fetched

dredmor.com resolves to 44.235.55.16, announced in 44.224.0.0/11 by AMAZON-02 - Amazon.com, Inc. in US. dredmor.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 · dredmor.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/dredmor.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
c/o respectmyprivacy,
Contact emails
dredmor.com@respectmyprivacy.com, 62b606db-2901-4c83-91d0-82ecd9126224@identity-protect.org, 7ace3c3e-e6a7-45ec-8db7-415e4b5dc744@identity-protect.org, d52b3ff2-5e93-45d2-a9ad-b65a43cc42c6@identity-protect.org, f429df9b-bbc7-4fab-9209-b8e42bcffdd1@identity-protect.org

Subdomains

Subdomain
mailing-list.dredmor.com
talkative-snail.dredmor.com
wildcard.dredmor.com
www.dredmor.com

Showing 4 of 4 subdomains (4 per page).

Mail and authentication

Nameservers

  • ns-322.awsdns-40.com
  • ns-944.awsdns-54.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
  • ns-1074.awsdns-06.org
  • ns-1785.awsdns-31.co.uk

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

Threat-feed evidence

History

Related pages

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