Skip to content

Hostname

postdonbass.com

Last fetched

postdonbass.com resolves to 31.133.59.253, announced in 31.133.59.0/24 by UGLETELECOM-AS - STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "UGLETELECOM" in RU. postdonbass.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 · postdonbass.comRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/postdonbass.com

Resolution chain

IPv6 resolution

No AAAA record for postdonbass.com is recorded in WhisperGraph.

Attribution

state unitary enterprise of donetsk people republic ugletelecom

ORIGIN_AS

WHOIS identity

Registrar
iana:1606
Registrant organisation
personal data, can not be publicly disclosed according to applicable laws.
Contact emails
zhukov.d@level-msk.com, priemnaya-donbasspost@postdonbass.com, administrator@minsvyazdnr.ru, administrator@msdnr.ru, postdonbass.com@regprivate.ru

Subdomains

Subdomain
1c-online.postdonbass.com
mail.postdonbass.com
proxy.postdonbass.com
redmine.postdonbass.com
shop.postdonbass.com
wildcard.postdonbass.com
www.postdonbass.com

Showing 7 of 7 subdomains (7 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns0.ugletele.com
  • ns1.ugletele.com
  • ns2.ugletele.com
  • ns3.ugletele.com

MX records

  • mx05.ugletele.com
  • mx10.ugletele.com
  • mx20.ugletele.com

SPF policy

  • a: postdonbass.com
  • mx: postdonbass.com
  • include: ugletele.com

Threat-feed evidence

History

Related pages

Pivot from postdonbass.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: "postdonbass.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.