Hostname
huskerboard.com
Last fetched
huskerboard.com resolves to 162.254.119.14, announced in 162.254.116.0/22 by HOSTDUPLEX - Host Duplex, LLC in US. huskerboard.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
IPv6 resolution
Attribution
duplex
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1479
- Registrant organisation
- college sports,
- Contact emails
- info@collegesportsinc.com, pw-18481ce31f1f19804b556fe5418a506d@privacyguardian.org, pw-505b459b7a559b8cd3537f952dc7ee5a@privacyguardian.org, pw-ad70b0e1d70d138451847f0f662483e7@privacyguardian.org
Subdomains
| Subdomain |
|---|
| cpanel.huskerboard.com |
| cpcalendars.huskerboard.com |
| cpcontacts.huskerboard.com |
| mail.huskerboard.com |
| webdisk.huskerboard.com |
| webmail.huskerboard.com |
| whm.huskerboard.com |
| www.huskerboard.com |
Showing 8 of 8 subdomains (8 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
- ns1.hostduplex.com
- ns2.hostduplex.com
- ns3.hostduplex.com
- ns1.thinline.cz
- ns2.thinline.cz
- ns3.cesky-hosting.eu
- 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.huskerboard.com
- mx1b20.thinline.cz
- mx1d10.thinline.cz
SPF policy
- ip: 184.154.196.0/24
- ip: 76.79.56.224/27
- a: huskerboard.com
- mx: huskerboard.com
- include: spf.cesky-hosting.cz
- a: mail.rapidemail.net
- ip: 162.254.117.109
- ip: 162.254.119.14
- ip: 96.127.166.218
Threat-feed evidence
History
Related pages
Pivot from huskerboard.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: "huskerboard.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.