Skip to content

Hostname

iptcom.net

Last fetched

iptcom.net resolves to 92.63.99.5, announced in 92.63.96.0/21 by RU-JSCIOT - JSC IOT in RU. iptcom.net 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 · iptcom.netRouting diversity1.5/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint7.4/10canon.whisper.security/host/iptcom.net

Resolution chain

IPv6 resolution

No AAAA record for iptcom.net is recorded in WhisperGraph.

Attribution

jsc iot

ORIGIN_AS

WHOIS identity

Registrar
iana:1112
Registrant organisation
privacy protection service
Contact emails
hostmaster@imena.ua

Subdomains

Mail and authentication

Nameservers

  • ns0.1984.is
  • ns1.1984.is
  • ns1.he.net
  • ns3.he.net
  • ns4.he.net
  • ns2.afraid.org
  • we.hostmaster.ua
  • nb.yz.kiev.ua
  • nebule.yz.kiev.ua
  • ns3.yz.kiev.ua
  • ns.secondary.net.ua
  • ns.vc.org.ua

MX records

  • mail.iptcom.net
  • nebule.yz.kiev.ua

SPF policy

  • redirect: _spf.yz.kiev.ua

Threat-feed evidence

History

Related pages

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