Hostname
nibud.nl
Last fetched
nibud.nl resolves to 3 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists registrar:realtime register|ceintuurbaan 32a|8024aa zwolle|netherlands|| as the registrar.
Nutrition Label
Resolution chain
nibud.nl resolves to 3 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.26.6.234 | 104.26.0.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 104.26.7.234 | 104.26.0.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.75.72 | 172.67.64.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- registrar:realtime register|ceintuurbaan 32a|8024aa zwolle|netherlands||
- Organization
- —
- Contact emails
- —
Subdomains
67 observed subdomains of nibud.nl.
Showing 25 of 67. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from nibud.nl in the public web crawl.
3,703 sites link to this hostname.
212 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
9 SPF mechanisms authorising senders for nibud.nl.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf-ssg-a.microsoft.com |
| SPF_INCLUDE | _spf.spotler.email |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | mailgun.org |
| SPF_IP | 213.154.242.43 |
| SPF_IP | 2a02:2770:17:0:21a:4aff:feed:bc5a |
| SPF_IP | 2a03:9700:8000:0:0:0:0:111 |
| SPF_IP | 31.7.4.111 |
| SPF_IP | 84.22.106.173/32 |
Related pages
Pivot deeper into the graph from nibud.nl.
- IP · 104.26.6.234
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · registrar:realtime register|ceintuurbaan 32a|8024aa zwolle|netherlands||
- Country · CA
- TLD · .nl
- Browse hostnames · ni…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "nibud.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.