Skip to content

Hostname

amts.pk

Last fetched

amts.pk resolves to 31.207.47.56, announced in 31.207.47.0/24 by HOSTKEY-AS - HOSTKEY B.V. in NL. amts.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 · amts.pkRouting diversity2.4/10Peering density7.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/amts.pk

Resolution chain

IPv6 resolution

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

Attribution

hostkey

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for amts.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
api.amts.pk
cloud.amts.pk
fbr.amts.pk
mail.amts.pk
webdisk.amts.pk
webmail.amts.pk
www.amts.pk

Showing 7 of 7 subdomains (7 per page).

Mail and authentication

Nameservers

  • ns1.hostnext.net
  • ns2.hostnext.net

MX records

  • mail.amts.pk

SPF policy

  • include: relay.mailchannels.net
  • a: amts.pk
  • mx: amts.pk
  • ip: 217.79.245.246
  • ip: 31.207.47.56
  • ip: 5.9.110.142

Threat-feed evidence

History

Related pages

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