Hostname
113.nl
Last fetched
113.nl resolves to 6 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists registrar:team.blue nl b.v. as the registrar.
Nutrition Label
Resolution chain
113.nl resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.21.32.42 | 104.21.32.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.182.203 | 172.67.176.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.96.1 | 188.114.96.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.96.3 | 188.114.96.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.97.1 | 188.114.97.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.97.3 | 188.114.97.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- registrar:team.blue nl b.v.
- Organization
- —
- Contact emails
- —
Subdomains
52 observed subdomains of 113.nl.
Showing 25 of 52. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from 113.nl in the public web crawl.
2,092 sites link to this hostname.
229 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
18 SPF mechanisms authorising senders for 113.nl.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | one.zoho.eu |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.afas.online |
| SPF_INCLUDE | spf.eprov.nl |
| SPF_INCLUDE | spf.exclaimer.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 149.210.144.108 |
| SPF_IP | 149.210.146.79 |
| SPF_IP | 149.210.146.80 |
| SPF_IP | 149.210.190.32 |
| SPF_IP | 149.210.190.34 |
| SPF_IP | 149.210.202.18 |
| SPF_IP | 2a01:7c8:aab1:353:0:0:0:1 |
| SPF_IP | 37.34.61.136 |
| SPF_IP | 37.97.227.48 |
| SPF_IP | 46.244.7.12 |
| SPF_IP | 46.244.7.13 |
| SPF_IP | 5.79.108.218 |
Related pages
Pivot deeper into the graph from 113.nl.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "113.nl"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.