Skip to content

Hostname

derekmelder.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of derekmelder.com owner
Contact emails
411562a9-a596-4c60-b396-c412f92bb8e5@identity-protect.org, 946bfe29-6cad-4d00-b643-f13e0e26e9f4@identity-protect.org, a353d53e-0dd7-4608-8c8c-5bf3babe0a92@identity-protect.org, d21d87cb-b351-4dd0-af79-32b6767dd319@identity-protect.org, d7bc9bcd-6396-4206-94ad-841c71bade3c@identity-protect.org, f6b4bf6b-4511-4cec-9a3b-df3cb588e06f@identity-protect.org, owner-10488565@derekmelder.com.whoisprivacyservice.org

Subdomains

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • ns-206.awsdns-25.com
  • ns-555.awsdns-05.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-1453.awsdns-53.org
  • ns-1659.awsdns-15.co.uk

MX records

  • mx.zoho.com
  • mx2.zoho.com
  • mx3.zoho.com

SPF policy

  • include: zoho.com

Threat-feed evidence

History

Related pages

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