Skip to content

Hostname

tftheft.pk

Last fetched

tftheft.pk resolves to 163.61.25.3, announced in 163.61.25.0/24 by PITC1-AS-AP - PITC in PK. tftheft.pk 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 · tftheft.pkRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/tftheft.pk

Resolution chain

IPv6 resolution

No AAAA record for tftheft.pk is recorded in WhisperGraph.

Attribution

pitc

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for tftheft.pk. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
history.tftheft.pk
mail.tftheft.pk
www.tftheft.pk

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns1.discozdata.org
  • ns2.discozdata.org

MX records

  • mail.tftheft.pk

SPF policy

  • a: tftheft.pk
  • mx: tftheft.pk
  • a: mail.tftheft.pk

Threat-feed evidence

History

Related pages

Pivot from tftheft.pk 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: "tftheft.pk"})-[: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.