Skip to content

Hostname

easytap.com

Last fetched

easytap.com resolves to 62.3.44.11, announced in 62.3.44.0/24 by Inleed - Yelles AB in US. easytap.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 · easytap.comRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/easytap.com

Resolution chain

IPv6 resolution

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

Attribution

yelles

ORIGIN_AS

WHOIS identity

Registrar
iana:3867
Registrant organisation
christer johansson
Contact emails
cj@hth.com, info@domain-contact.org, 2d56d391a32f289810f757f9759f0d53be1868ec7701ad9299e8b4a34ba003e5@easytap.com.whoisproxy.org, 6be6157faee1c7d42ef3c80ef880f043d5936e4db19dbbe9dc86f762b1a51d0d@easytap.com.whoisproxy.org, 74dc7aa43dd207ebe8efb6569b739ab5e9e0cd8d81c6e4c795b85bba8374c9ed@easytap.com.whoisproxy.org, b8c3546bd40a79a46b827855a9ef966ba4864c9a19cd80145a797077f5a2eb0f@easytap.com.whoisproxy.org, fdf2040cd276ab160ae0aeffd6e96a3822389e8d42d2df186cd424be7a0de68f@easytap.com.whoisproxy.org

Subdomains

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns1.inleed.net
  • ns2.inleed.net
  • ns3.inleed.net
  • ns4.inleed.net
  • ns5.inleed.net
  • ns6.inleed.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

MX records

  • mail.easytap.com

SPF policy

  • a: easytap.com
  • mx: easytap.com
  • include: spf.inleed.se
  • ip: 62.3.44.11

Threat-feed evidence

History

Related pages

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