46.31.90.61
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.
- Baseline (neutral) 65
- Long-established allocation (16y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- testapi.realdolmencloud.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-10-01 02:02 UTC
- Forward DNS last checked
- 2026-09-30 14:36 UTC
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
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.
Reverse-DNS changes between Sep 30, 2026 and Oct 1, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- testapi.realdolmencloud.com — since at least Oct 1, 2026 → present
- azure_aps_invoice.realdolmencloud.com — Sep 30, 2026 → Oct 1, 2026
- testapi.realdolmencloud.com — Sep 30, 2026 → Sep 30, 2026
- publicinvoice1.realdolmencloud.com — Sep 29, 2026 → Sep 30, 2026
- testinvoice.realdolmencloud.com — Sep 29, 2026 → Sep 29, 2026
- testapi.realdolmencloud.com — Sep 29, 2026 → Sep 29, 2026
- publicinvoice1.realdolmencloud.com.realdolmencloud.com — Sep 28, 2026 → Sep 29, 2026
- accinvoice.realdolmencloud.com — Sep 27, 2026 → Sep 28, 2026
- publicinvoice1api.realdolmencloud.com.realdolmencloud.com — Sep 27, 2026 → Sep 27, 2026
- accinvoice.realdolmencloud.com — Sep 27, 2026 → Sep 27, 2026
- publicinvoice.realdolmencloud.com — Sep 27, 2026 → Sep 27, 2026
- azure_aps_invoice.realdolmencloud.com — Sep 25, 2026 → Sep 27, 2026
- publicinvoice1api.realdolmencloud.com.realdolmencloud.com — Sep 25, 2026 → Sep 25, 2026
- publicinvoiceapi.realdolmencloud.com — Aug 25, 2026 → Sep 25, 2026
- accinvoice.realdolmencloud.com — Aug 24, 2026 → Aug 25, 2026
- api.realdolmencloud.com — Aug 19, 2026 → Aug 24, 2026
- azure_aps_invoice.realdolmencloud.com — Aug 18, 2026 → Aug 19, 2026
- publicinvoice1.realdolmencloud.com — Aug 17, 2026 → Aug 18, 2026
- accinvoice.realdolmencloud.com — Jul 10, 2026 → Aug 17, 2026
- api.realdolmencloud.com — Jul 7, 2026 → Jul 10, 2026
- invoicing.realdolmencloud.com — Jul 3, 2026 → Jul 7, 2026
- publicinvoice1.realdolmencloud.com.realdolmencloud.com — Jun 29, 2026 → Jul 3, 2026
- api.realdolmencloud.com — Jun 24, 2026 → Jun 29, 2026
- publicinvoiceapi.realdolmencloud.com — Jun 16, 2026 → Jun 24, 2026
- publicinvoice.realdolmencloud.com — Jun 13, 2026 → Jun 16, 2026
Network Allocation for 46.31.90.61
- CIDR range
- 46.31.88.0/21
- IP range (int)
- 773,806,080 — 773,808,127
- Prefix length
- /21
- Organization
- Inetum Belgium NV
- ASN
- AS196987
- ASN name
- Inetum Belgium NV
- Location
- Antwerp, Flanders, Belgium
- Coordinates
- 50.850900, 4.344700
- Accuracy radius
- 100 km
- Postal code
- 2000
- Regional Internet Registry
- RIPE
- Allocated
- 2010-09-16
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-09-23 05:21:49
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 46.31.90.61?
46.31.90.61 is allocated to Inetum Belgium NV (AS196987), registered in Antwerp, Belgium.
Where is 46.31.90.61 located?
The geolocation for 46.31.90.61 maps to Antwerp, Belgium 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 46.31.90.61 on?
46.31.90.61 belongs to the 46.31.88.0/21 network block announced by AS196987. This range contains 2,048 addresses.
Does 46.31.90.61 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.
