188.116.26.13
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 (17y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- discord.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-09-18 09:52 UTC
- Forward DNS last checked
- 2026-09-18 09:52 UTC
Forward DNS records for discord.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 162.159.128.233 | — | 300s |
| A | 162.159.135.232 | — | 300s |
| A | 162.159.136.232 | — | 300s |
| A | 162.159.137.232 | — | 300s |
| A | 162.159.138.232 | — | 300s |
| MX | alt1.aspmx.l.google.com | 5 | — |
| MX | alt2.aspmx.l.google.com | 5 | — |
| MX | aspmx.l.google.com | 1 | — |
| MX | aspmx2.googlemail.com | 10 | — |
| MX | aspmx3.googlemail.com | 10 | — |
| NS | gabe.ns.cloudflare.com | — | — |
| NS | sima.ns.cloudflare.com | — | — |
| TXT | apple-domain-verification=UP89cBit9taWldL9 | — | — |
| TXT | atlassian-domain-verification=JNe2Ze7P8p623k8f7xRaHDyQWb6VzLxjFga1tu8M7lmVXC0bo1XgdnEsYuGIRFHv | — | — |
| TXT | docusign=90632817-c176-45ac-9297-96916059c0c5 | — | — |
| TXT | google-site-verification=19lneLj60qA3xv2S96DiWzeNjLZZca3otEPR6KhvrBQ | — | — |
| TXT | google-site-verification=4lTw99D7TJimzNkaj9WtUoOpZoXad73hmD4WgR7COH4 | — | — |
| TXT | google-site-verification=AkZq_nCggw5fS3x2crQxF9I_9MEdqqWIVB-mutOiFzw | — | — |
| TXT | google-site-verification=P3cQmz_2xQ17u5qOBHf7JIAYGq3HzDq0UtEkbOR6ZjQ | — | — |
| TXT | google-site-verification=Xos4rv9-rY3aGpQ6FtxhUC_Buhef0wF88_4rB4HmTZI | — | — |
| TXT | google-site-verification=uv4vY9gTOxCxIHlq_V75SMEEvcU44ATbkPcmV0Cpvus | — | — |
| TXT | slack-domain-verification=hb2Jt7Z5kT0NqJOuGUM2P6L3ZihqWD3wR17JuECt | — | — |
| TXT | v=DMARC1; p=reject | — | — |
| TXT | v=DMARC1; p=reject; rua=mailto:b0450def5eb44238a7059f24059a4585@dmarc-reports.cloudflare.net; | — | — |
| TXT | v=spf1 include:_spf.google.com include:mail.zendesk.com include:sendgrid.net include:3885857.spf06.hubspotemail.net ip4:198.2.180.60 -all | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 188.116.26.13
- CIDR range
- 188.116.24.0/22
- IP range (int)
- 3,161,724,928 — 3,161,725,951
- Prefix length
- /22
- Organization
- Scalaxy B.V.
- ASN
- AS58061
- ASN name
- Scalaxy B.V.
- Location
- Amsterdam, North Holland, The Netherlands
- Coordinates
- 52.371600, 4.888300
- Accuracy radius
- 20 km
- Postal code
- 1012
- Regional Internet Registry
- RIPE
- Allocated
- 2009-05-29
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-09-18 05:25:17
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured weekly from regional internet registry (RIR) delegation files for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | Country Change | NL | AE |
See the full history for 188.116.24.0/22.
Frequently Asked Questions
Who owns 188.116.26.13?
188.116.26.13 is allocated to Scalaxy B.V. (AS58061), registered in Amsterdam, The Netherlands.
Where is 188.116.26.13 located?
The geolocation for 188.116.26.13 maps to Amsterdam, The Netherlands 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 188.116.26.13 on?
188.116.26.13 belongs to the 188.116.24.0/22 network block announced by AS58061. This range contains 1,024 addresses.
Does 188.116.26.13 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.
