Hostname
shodor.org
Last fetched
shodor.org resolves to 204.85.28.50, announced in 204.84.0.0/15 by NCREN - MCNC in US. shodor.org 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
No AAAA record for shodor.org is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:99
- Registrant organisation
- shodor education foundation,
- Contact emails
- 015o2v7v7491@filteredemailaddress.com, 07869x3147@nojunkemailaddress.com, 111e476513@junkemailprevention.com, 3202598b8952@filteredemailaddress.com, 3262046y5496@junkemailprevention.com, 3t2a8b0335@nojunkemailaddress.com, 613u85980167@nojunkemailaddress.com, 615e5r7s5489@nojunkemailaddress.com, 6j6f7r7602@nojunkemailaddress.com, 7k1e0m4560@nojunkemailaddress.com, 917u0x8310@junkemailprevention.com, 9e65747127@eliminatejunkemail.com, 9i9z1b8443@filteredemailaddress.com, 9t9u2j4213@eliminatejunkemail.com
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
- ns01.netlifydns.com
- ns02.netlifydns.com
- ns03.netlifydns.com
- ns04.netlifydns.com
- dns1.p04.nsone.net
- dns2.p04.nsone.net
- dns3.p04.nsone.net
- dns4.p04.nsone.net
- cell.shodor.org
- scan.shodor.org
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
- mail1.shodor.org
- mail2.shodor.org
SPF policy
- include: _spf.google.com
- a: mail.shodor.org
- ip: 204.85.28.16
- ip: 204.85.28.19
- ip: 204.85.28.20
- ip: 204.85.28.7
- ip: 204.85.29.16
- ip: 204.85.29.6
Threat-feed evidence
History
Related pages
Pivot from shodor.org 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: "shodor.org"})-[: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.