Skip to content

Hostname

2inchcock.com

Last fetched

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

Resolution chain

IPv6 resolution

No AAAA record for 2inchcock.com is recorded in WhisperGraph.

Attribution

amazon com

ORIGIN_AS

WHOIS identity

Registrar
iana:228
Registrant organisation
dnr
Contact emails
info@xenya.com, 48b148cfd7bf1ce346909c9978578446b63f22c03c5d7fd3963d59ef857fc29f@2inchcock.com.whoisproxy.org, 49f431fe79b747e8fe08c2219cccd6eeca7d76ebfef517ff629cda6717281527@2inchcock.com.whoisproxy.org, 4c09f19a980861a087557663ce0dc15d456a97d19b4e6f840781bbe8a4dc7c78@2inchcock.com.whoisproxy.org, 837688f5ecd1f480deda7fa11be83ca2af8a96d7fe088bf15e6169de7e35a2bd@2inchcock.com.whoisproxy.org, 8719f73ee1aeb5c9e3894160f5654b3bdfbef1f6b0b87f9369c6e042c6ae9fda@2inchcock.com.whoisproxy.org, b50c680fd481cf8d613b950a0ffc87110fa6318471c92becbfa841e6b51eb98a@2inchcock.com.whoisproxy.org, c276399980a121e1acf27a006bcf779f7defd3d23b53635eb074cd2088bc264b@2inchcock.com.whoisproxy.org, cc0e96610da94d7789668635648f6f2ed295eb1a0adb569f066be48485c6e123@2inchcock.com.whoisproxy.org, deb4b6e94596f2a1ddc7896b62459698a4c1152fcf33ea9a2b2055d1799dc13e@2inchcock.com.whoisproxy.org, fd6dfc8d5d0ff35196e3f77fab6d1ce4e5cefeab43ae3b3f470332443eda7f18@2inchcock.com.whoisproxy.org

Mail and authentication

Nameservers

  • ns1.monikerdns.net
  • ns2.monikerdns.net
  • ns3.monikerdns.net
  • ns4.monikerdns.net

Threat-feed evidence

History

Related pages

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