Skip to content

Hostname

spencer.org

Last fetched

spencer.org resolves to 109.228.54.96, announced in 109.228.0.0/18 by IONOS-AS - IONOS SE in GB. spencer.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · spencer.orgRouting diversity1.5/10Peering density6.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.0/10canon.whisper.security/host/spencer.org

Resolution chain

IPv6 resolution

No AAAA record for spencer.org is recorded in WhisperGraph.

Attribution

ionos se

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
rc9gg6tn3kx@networksolutionsprivateregistration.com, w54e829t2ej@networksolutionsprivateregistration.com, is@spencer.org, jcraven@spencer.org

Subdomains

Subdomain
annualreview.spencer.org
autodiscover.spencer.org
prototype.spencer.org
sslvpn.spencer.org
www.spencer.org

Showing 5 of 5 subdomains (5 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

Sample outbound links

Mail and authentication

Nameservers

  • ns20.digicertdns.com
  • ns10.dnsmadeeasy.com
  • ns11.dnsmadeeasy.com
  • ns12.dnsmadeeasy.com
  • ns13.dnsmadeeasy.com
  • ns14.dnsmadeeasy.com
  • ns15.dnsmadeeasy.com

MX records

  • d333132a.ess.barracudanetworks.com
  • d333132b.ess.barracudanetworks.com
  • spencer-org.mail.protection.outlook.com

SPF policy

  • ip: 107.6.0.56/32
  • include: spf.ess.barracudanetworks.com
  • include: _spf.intacct.com
  • include: spf.protection.outlook.com
  • include: e2ma.net
  • ip: 107.6.0.57
  • ip: 107.6.40.137

Threat-feed evidence

History

Related pages

Pivot from spencer.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: "spencer.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.