Skip to main content
CIDR
/21 · 2.0K IPs
ASN
Hostkey B.v.
Reverse DNS
zivile-schutzmacht.org
Last scanned 5 days ago
Blocklisted
Checking…
Scanning blocklists

Reputation · trust score

A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.

85/100
Trusted
How this score is built

Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →

DNS records

Reverse DNS (PTR)
zivile-schutzmacht.org
Forward-confirmed (FCrDNS)
✗ Mismatch
PTR TTL
3600 s
Reverse DNS last checked
2026-10-05 19:39 UTC
Forward DNS last checked
2026-10-05 19:39 UTC

Forward DNS records for zivile-schutzmacht.org

TypeValuePriorityTTL
A 31.192.108.38 — 172800s
NS ns1.domain-hosting.name — —
NS ns2.domain-hosting.name — —
NS ns3.domain-hosting.name — —
NS ns4.domain-hosting.name — —
every IP & sub-domain we've seen under this domain

Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.

Domains hosted

as of 2026-10-04 UTC

0

issued.live saw no domain resolving to this IP in its latest weekly snapshot.

Domain data provided by issued.live — for full details visit https://issued.live/pricing

Reverse DNS history

How this IP's reverse DNS (PTR) has changed over time, from our scans.

This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.

  1. zivile-schutzmacht.org — Oct 5, 2026 → present
  2. mail.zivile-schutzmacht.org — Oct 5, 2026 → Oct 5, 2026
  3. zivile-schutzmacht.org — Oct 5, 2026 → Oct 5, 2026
  4. mail.zivile-schutzmacht.org — Oct 4, 2026 → Oct 5, 2026
  5. zivile-schutzmacht.org — Oct 3, 2026 → Oct 4, 2026
  6. mail.zivile-schutzmacht.org — Oct 3, 2026 → Oct 3, 2026
  7. zivile-schutzmacht.org — Oct 1, 2026 → Oct 3, 2026
  8. mail.zivile-schutzmacht.org — Oct 1, 2026 → Oct 1, 2026
  9. zivile-schutzmacht.org — Sep 29, 2026 → Oct 1, 2026
  10. mail.zivile-schutzmacht.org — Sep 29, 2026 → Sep 29, 2026
  11. zivile-schutzmacht.org — Sep 28, 2026 → Sep 29, 2026
  12. mail.zivile-schutzmacht.org — Sep 27, 2026 → Sep 28, 2026
  13. no PTR — Sep 26, 2026 → Sep 27, 2026
  14. mail.zivile-schutzmacht.org — Sep 25, 2026 → Sep 26, 2026
  15. zivile-schutzmacht.org — Aug 24, 2026 → Sep 25, 2026
  16. mail.zivile-schutzmacht.org — Aug 24, 2026 → Aug 24, 2026
  17. zivile-schutzmacht.org — Aug 18, 2026 → Aug 24, 2026
  18. mail.zivile-schutzmacht.org — Jul 2, 2026 → Aug 18, 2026
  19. zivile-schutzmacht.org — Jun 28, 2026 → Jul 2, 2026
  20. mail.zivile-schutzmacht.org — Jun 21, 2026 → Jun 28, 2026
  21. zivile-schutzmacht.org — Jun 15, 2026 → Jun 21, 2026
  22. mail.zivile-schutzmacht.org — Jun 13, 2026 → Jun 15, 2026

Network Allocation for 31.192.108.38

CIDR range
31.192.104.0/21
IP range (int)
532,703,232 — 532,705,279
Prefix length
/21
Organization
Hostkey B.v.
ASN
AS50867
ASN name
Hostkey B.v.
Location
Moscow, Moscow, Russia
Coordinates
55.748700, 37.618700
Accuracy radius
20 km
Postal code
101000
Regional Internet Registry
RIPE
Allocated
2011-04-21
Data source(s)
maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
Last updated
2026-09-30 08:42:22

Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.

Announced prefix
Origin AS
Announcement samples
15,522
Last seen
2026-10-06 02:27:32

Frequently Asked Questions

Who owns 31.192.108.38?

31.192.108.38 is allocated to Hostkey B.v. (AS50867), registered in Moscow, Russia.

Where is 31.192.108.38 located?

The geolocation for 31.192.108.38 maps to Moscow, Russia based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.

What network is 31.192.108.38 on?

31.192.108.38 belongs to the 31.192.104.0/21 network block announced by AS50867. This range contains 2,048 addresses.

Does 31.192.108.38 have a reverse DNS record?

Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.

Neighbors

Other addresses in the same /24.

Related

Last updated: 2026-09-30 20:45:58 UTC
Share