Skip to content

Hostname

ndream.com

Last fetched

ndream.com resolves to 54.69.129.135, announced in 54.68.0.0/15 by AMAZON-02 - Amazon.com, Inc. in US. ndream.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 · ndream.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/ndream.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of ndream.com owner
Contact emails
pangdh@ndream.com, stpark5525@gmail.com, 03baee18-46b4-4589-8d03-a99e5f654be4@identity-protect.org, 1b1523d9-eec5-4e1f-a89e-14dd5038aa6a@identity-protect.org, 7a35fb15-f7d3-47bf-b6f9-0b5007ea29de@identity-protect.org, 9287f2ee-23a3-46d2-8e59-ae7226ceb9e6@identity-protect.org, 9f9d668c-4860-4a74-ae02-827e861219ce@identity-protect.org, ad8b397f-e3a4-4b2c-a670-64986f404840@identity-protect.org, ae1a3cc6-ae69-40ab-a65b-64b8e009b7bd@identity-protect.org, owner-126171@ndream.com.whoisprivacyservice.org

Subdomains

Subdomain
bookstack.ndream.com
change-pw.ndream.com
gw.ndream.com
mail.ndream.com
tool.ndream.com
vpn.ndream.com

Showing 6 of 6 subdomains (6 per page).

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

  • ns-21.awsdns-02.com
  • ns-1021.awsdns-63.net
  • ns-1447.awsdns-52.org
  • ns-1936.awsdns-50.co.uk

MX records

  • ndream-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • ip: 61.43.45.137

Threat-feed evidence

History

Related pages

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