Hostname
nobodesign.com
Last fetched
nobodesign.com resolves to 104.26.12.68, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. nobodesign.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.26.12.68
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.13.68
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.40.197
172.66.40.0/21 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.43.59
172.66.40.0/21 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.72.23
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 8.47.69.0
8.47.69.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Bratislava, SK
- 8.6.112.0
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:73
- Registrant organisation
- nobo design ab
- Contact emails
- whois.privacy@privacyid.com, joakim@umbragroup.se
Subdomains
| Subdomain |
|---|
| sst.nobodesign.com |
| www.nobodesign.com |
Showing 2 of 2 subdomains (2 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- novalee.ns.cloudflare.com
- patrick.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mx.ilait.se
- nobodesign-com.mail.protection.outlook.com
SPF policy
- include: spf.mandrillapp.com
- include: _spf.ilait.net
- include: servers.mcsv.net
- include: _spf.specter.se
Threat-feed evidence
History
Related pages
Pivot from nobodesign.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "nobodesign.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.