Skip to content

Hostname

screwattack.com

Last fetched

screwattack.com resolves to 192.64.119.252, announced in 192.64.119.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. screwattack.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 · screwattack.comRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/screwattack.com

Resolution chain

IPv6 resolution

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

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
on behalf of screwattack.com owner
Contact emails
screwattack.com@domainsbyproxy.com, hostmaster@roosterteeth.com, 643e483e-6a3a-4f7e-818f-6ff4994f96fa@identity-protect.org, 99908f3a-4cb2-4411-9278-ecfba9340361@identity-protect.org, b20f30cc-d69e-405e-a032-4dde8ba00fa3@identity-protect.org, e69b56e1-9de0-419d-864e-b1de0fa5a707@identity-protect.org, f5e115d4-88a6-42df-9ac0-f057b9980163@identity-protect.org, owner-2809682@screwattack.com.whoisprivacyservice.org, owner-433505@screwattack.com.whoisprivacyservice.org, owner-4344663@screwattack.com.whoisprivacyservice.org, owner-5867097@screwattack.com.whoisprivacyservice.org, owner-5939664@screwattack.com.whoisprivacyservice.org, owner-6209613@screwattack.com.whoisprivacyservice.org, owner-747350@screwattack.com.whoisprivacyservice.org, owner-8679256@screwattack.com.whoisprivacyservice.org

Subdomains

Showing 1 of 1 subdomain (1 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

Threat-feed evidence

History

Related pages

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