Skip to content

Hostname

admin.panditrans.com

Last fetched

admin.panditrans.com resolves to 79.137.229.118, announced in 79.137.251.0/24 by DINET-AS - LLC Digital Network in RU. admin.panditrans.com 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 · admin.panditrans.comRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.5/10canon.whisper.security/host/admin.panditrans.com

Resolution chain

IPv6 resolution

No AAAA record for admin.panditrans.com is recorded in WhisperGraph.

Attribution

dinet

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for admin.panditrans.com. 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.

Mail and authentication

Nameservers

  • 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
  • ns1.dns2b.ru
  • ns3.dns2dns.ru
  • ns4.dns4dns.ru
  • ns2.dns4u.ru
  • ns5.l3o-dns.ru

MX records

  • mail.panditrans.com
  • mx1.panditrans.com
  • mx2.panditrans.com

SPF policy

  • a: admin.panditrans.com
  • mx: admin.panditrans.com
  • ip: 188.246.191.90
  • ip: 212.248.60.130
  • ip: 212.48.32.214
  • ip: 213.248.39.196
  • ip: 213.248.39.198
  • ip: 95.163.111.104
  • ip: 95.163.111.106
  • ip: 95.163.136.192
  • ip: 95.163.136.194

Threat-feed evidence

History

Related pages

Pivot from admin.panditrans.com 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: "admin.panditrans.com"})-[: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.