Hostname
norbi.app
Last fetched
norbi.app resolves to 104.21.50.72, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. norbi.app 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.21.50.72
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.158.204
172.67.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
Subdomains
| Subdomain |
|---|
| autoconfig.norbi.app |
| autodiscover.norbi.app |
| identity-dr.norbi.app |
| openbao-dr.norbi.app |
| welcome.norbi.app |
| www.norbi.app |
Showing 6 of 6 subdomains (6 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
- rocket.seo-anomaly-anchor.online
- rocket.seo-anomaly-conversion.online
- rocket.seo-anomaly-crawlbudget.online
- rocket.seo-anomaly-crawling.online
- rocket.seo-anomaly-ctr.online
- rocket.seo-anomaly-domain.online
- rocket.seo-anomaly-engagement.online
- rocket.seo-anomaly-hreflang.online
- rocket.seo-anomaly-keydensity.online
- rocket.seo-anomaly-linkbuilding.online
Mail and authentication
Nameservers
- nicole.ns.cloudflare.com
- sean.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
- mail.polyverse.life
SPF policy
- a: norbi.app
- mx: norbi.app
- a: mail.polyverse.life
- ip: 95.179.251.21
Threat-feed evidence
History
Related pages
Pivot from norbi.app 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: "norbi.app"})-[: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.