Skip to content

Hostname

basicsofhacking.com

Last fetched

basicsofhacking.com resolves to 64.98.135.9, announced in 64.98.135.0/24 by TUCOWS-3 - Tucows.com Co. in CA. basicsofhacking.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 · basicsofhacking.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/basicsofhacking.com

Resolution chain

IPv6 resolution

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

Attribution

tucows com

ORIGIN_AS

WHOIS identity

Registrar
iana:48
Registrant organisation
whois agent
Contact emails
llntqrjcs@whoisprivacyprotect.com, trywtygrk@whoisprivacyprotect.com, twbcqlfs@whoisprivacyprotect.com

Subdomains

Subdomain
www.basicsofhacking.com

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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • dns1.name-services.com
  • dns2.name-services.com
  • dns3.name-services.com
  • dns4.name-services.com
  • dns5.name-services.com
  • 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

  • mx1.titan.email
  • mx2.titan.email

SPF policy

  • include: spf.titan.email

Threat-feed evidence

History

Related pages

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