Skip to content

Hostname

evevanguardtech.com

Last fetched

evevanguardtech.com resolves to 104.18.41.242, announced in 104.18.41.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. evevanguardtech.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 · evevanguardtech.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/evevanguardtech.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of evevanguardtech.com owner
Contact emails
322b7142-f6aa-45bc-8fd4-367e1558f0ca@identity-protect.org, 6bb64737-25a8-441e-8ce0-6b0ef1445a0c@identity-protect.org, d481a84e-084b-4183-841e-f0950bd89214@identity-protect.org, d491add5-a70f-43ac-874f-5152f8378da1@identity-protect.org, eccaa2ac-97a9-46fa-9845-6ffd1d072a8a@identity-protect.org

Subdomains

Subdomain
auth.evevanguardtech.com
dev.evevanguardtech.com
gameservers.evevanguardtech.com
production.evevanguardtech.com
services.evevanguardtech.com

Showing 5 of 13. View all subdomains →

Mail and authentication

Nameservers

  • ns-447.awsdns-55.com
  • aisha.ns.cloudflare.com
  • carmelo.ns.cloudflare.com
  • ns-656.awsdns-18.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-1356.awsdns-41.org
  • ns-1906.awsdns-46.co.uk

MX records

  • evevanguardtech-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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