Skip to content

Hostname

veonow.com

Last fetched

veonow.com resolves to 100.49.106.29, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. veonow.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 · veonow.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/veonow.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of veonow.com owner
Contact emails
veonow.com@domainsbyproxy.com, 2911cc03-3d18-4fe0-9e6d-7020ba847a49@identity-protect.org, 734be7ea-001c-4a21-b4c9-d34685c4861c@identity-protect.org, a92d280b-3812-4be0-aecc-440e633c9427@identity-protect.org

Subdomains

Subdomain
mdt.veonow.com
www.veonow.com

Showing 2 of 3. View all subdomains →

Mail and authentication

Nameservers

  • ns-360.awsdns-45.com
  • ns-547.awsdns-04.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-1245.awsdns-27.org
  • ns-1597.awsdns-07.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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