Skip to content

Hostname

test.paytech.systems

Last fetched

test.paytech.systems resolves to 71.218.238.64, announced in 71.218.0.0/16 by CENTURYLINK-US-LEGACY-QWEST - CenturyLink Communications, LLC in US. test.paytech.systems 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 · test.paytech.systemsRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/test.paytech.systems

Resolution chain

IPv6 resolution

No AAAA record for test.paytech.systems is recorded in WhisperGraph.

Attribution

centurylink

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for test.paytech.systems. 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-test.test.paytech.systems
backoffice-test.test.paytech.systems
c4c.test.paytech.systems
services-test.test.paytech.systems
static.test.paytech.systems

Showing 5 of 5 subdomains (5 per page).

Mail and authentication

Nameservers

  • ns1.dynu.com
  • ns2.dynu.com
  • ns3.dynu.com
  • ns4.dynu.com
  • ns5.dynu.com
  • ns6.dynu.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

Threat-feed evidence

History

Related pages

Pivot from test.paytech.systems 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: "test.paytech.systems"})-[: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.