Skip to content

Hostname

1stfucking.com

Last fetched

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

Resolution chain

IPv6 resolution

No AAAA record for 1stfucking.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:228
Registrant organisation
dnr
Contact emails
info@xenya.com, 0af6ccf5c24ab2527b50068b42fcb490ab30f3a84d60e5deb14026a6021f193d@1stfucking.com.whoisproxy.org, 2d3a76968caffcb6d7b22b204519f58e207cdbe79259b833952b7f64cb3ea225@1stfucking.com.whoisproxy.org, 35e4d09b7f470e5d489bea7f0bea722c3f7ab1103da1bb40df248a9c6a1861df@1stfucking.com.whoisproxy.org, 65d9cafbfb811f55630f69ebd3e23aba467da605f06b52f19b61c99efcf8ac1f@1stfucking.com.whoisproxy.org, 8c42bf52331591d7f237c74d97463f60256db17f1917458ce215f38397ed19de@1stfucking.com.whoisproxy.org, 955c464bbfaf05b3ba5b451525dde3cd691361e509b5f14279442f217b36a962@1stfucking.com.whoisproxy.org, aaaa724ecc941062561e1d3c8e6fa476e23613b803513122a7a1abd281e0e860@1stfucking.com.whoisproxy.org, dd7dc05a3469ed359d0beb406792a684baa8cc66ca172a3a9857322e810972b5@1stfucking.com.whoisproxy.org, f857f88d6b1adc195555f85d23867aa7aac58a4f2de922928d3d4c7432b34e48@1stfucking.com.whoisproxy.org, ffd4c9e74fef3c00276ddf255e7334fb0554909f2e32811675ea6a6530ddf035@1stfucking.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 1stfucking.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: "1stfucking.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.