Skip to content

Hostname

ns2.losspc.com

Last fetched

ns2.losspc.com resolves to 2 IPv4 addresses operated by AS63949 in US.

Nutrition Label

WHISPER CANON · ns2.losspc.comRouting diversity2.4/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/ns2.losspc.com

Resolution chain

ns2.losspc.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

WHOIS identity

No WHOIS records are currently associated with ns2.losspc.com in WhisperGraph.

Threat posture

History

Mail and authentication

SPF policy

14 SPF mechanisms authorising senders for ns2.losspc.com.

MechanismTarget
SPF_IP141.94.31.237
SPF_IP146.19.198.66
SPF_IP146.19.198.67
SPF_IP146.19.198.68
SPF_IP146.19.198.69
SPF_IP146.19.198.70
SPF_IP162.251.167.114
SPF_IP162.251.167.115
SPF_IP162.251.167.116
SPF_IP162.251.167.117
SPF_IP162.251.167.118
SPF_IP87.98.142.146
SPF_IP87.98.143.51
SPF_IP87.98.154.223

Related pages

Pivot deeper into the graph from ns2.losspc.com.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "ns2.losspc.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.