Hostname
incu.com
Last fetched
incu.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. incu.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
No IPv4 resolution is recorded for incu.com in WhisperGraph.
IPv6 resolution
No AAAA record for incu.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:48
- Registrant organisation
- brian wu
- Contact emails
- bcsrwcsbh@whoisprivacyprotect.com, brian@incu.com, clqkrnyyg@whoisprivacyprotect.com, dslyrwsy@whoisprivacyprotect.com, fjwxmstsfr@whoisprivacyprotect.com, jmjfbfdb@whoisprivacyprotect.com, kgvnftqwcw@whoisprivacyprotect.com, mpmcfjgqbs@whoisprivacyprotect.com, nnjblfqm@whoisprivacyprotect.com, twkdsdcwg@whoisprivacyprotect.com, brian.wu@incuclothing.com
Subdomains
Showing 12 of 106. View all subdomains →
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
- dns1.name-services.com
- dns2.name-services.com
- dns3.name-services.com
- dns4.name-services.com
- dns5.name-services.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
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- ip: 110.232.115.177/32
- include: cmail1.com
- include: _spf.google.com
- include: _spf.hostedemail.com
- include: spf.mandrillapp.com
- ip: 103.12.128.215
Threat-feed evidence
History
Related pages
Pivot from incu.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: "incu.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.