Skip to content

Hostname

gtschmidt.com

Last fetched

gtschmidt.com resolves to 104.21.35.39, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. gtschmidt.com 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 · gtschmidt.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/gtschmidt.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
aj5yh3f49sx@networksolutionsprivateregistration.com, b97px2ng4eb@networksolutionsprivateregistration.com, e98rm8sn8pb@networksolutionsprivateregistration.com, ec63q2z749b@networksolutionsprivateregistration.com, g99qr7v78rq@networksolutionsprivateregistration.com, kp68p8hx4xn@networksolutionsprivateregistration.com, sy8sn7xb423@networksolutionsprivateregistration.com, vb8fr3xt94u@networksolutionsprivateregistration.com, ys57v3hj92s@networksolutionsprivateregistration.com

Subdomains

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

Mail and authentication

Nameservers

  • anna.ns.cloudflare.com
  • reese.ns.cloudflare.com
  • ns1.bdm.microsoftonline.com
  • ns2.bdm.microsoftonline.com
  • ns3.bdm.microsoftonline.com
  • ns4.bdm.microsoftonline.com
  • ns49.worldnic.com
  • ns50.worldnic.com

MX records

  • gtschmidt-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: aspmx.pardot.com
  • include: _spf.salesforce.com
  • include: spf.mailanyone.net

Threat-feed evidence

History

Related pages

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

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