Skip to content

Hostname

pay1.paycode.com

Last fetched

pay1.paycode.com resolves to 1 IPv4 address operated by MTNNS-AS in ZA.

Nutrition Label

WHISPER CANON · pay1.paycode.comRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/pay1.paycode.com

Resolution chain

pay1.paycode.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
196.31.27.113196.30.0.0/15AS16637MTNNS-ASZA

WHOIS identity

No WHOIS records are currently associated with pay1.paycode.com in WhisperGraph.

Subdomains

1 observed subdomain of pay1.paycode.com.

Subdomain
www.pay1.paycode.com

Threat posture

History

Mail and authentication

SPF policy

7 SPF mechanisms authorising senders for pay1.paycode.com.

MechanismTarget
SPF_Apay1.paycode.com
SPF_INCLUDErelay.mailchannels.net
SPF_IP41.185.8.143/32
SPF_IP41.185.8.2
SPF_IP41.185.8.3
SPF_IP41.185.8.5
SPF_MXpay1.paycode.com

Related pages

Pivot deeper into the graph from pay1.paycode.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "pay1.paycode.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.