Skip to content

Hostname

verdn.com

Last fetched

verdn.com resolves to 216.150.1.129, announced in 216.150.1.0/24 by AMAZON-02 - Amazon.com, Inc. in US. verdn.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 · verdn.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/verdn.com

Resolution chain

IPv6 resolution

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

Attribution

amazon com

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
c/o whoisproxy.com
Contact emails
fa28d5c851eb42dfa54c1afa670c8c8a.protect@whoisguard.com, 252a1a2245e6442f99c33869c39498ef.protect@withheldforprivacy.com, be30a7bfe685483589dc2cf9c231893f.protect@withheldforprivacy.com, 4e2df35fde25ddb51c10563648ef89151a0b840d0b02da0aa8ce6d0f2d017b4b@verdn.com.whoisproxy.org

Subdomains

Subdomain
api-dais.verdn.com
api-staging.verdn.com
api.verdn.com
assets.verdn.com
blob.verdn.com
blog.verdn.com
cdn.verdn.com
dashboard.verdn.com
docs.verdn.com
hermes.verdn.com
jeff.verdn.com
library.verdn.com

Showing 12 of 30. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

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
  • nwzrdxaybj7aqw6xrkgtynxtq5cimihr54uiboxbagkfr45g2ewq.mx-verification.google.com

SPF policy

  • include: _spf.google.com
  • include: eu.mailgun.org

Threat-feed evidence

History

Related pages

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