Skip to content

Hostname

schweizerlust.com

Last fetched

schweizerlust.com resolves to 34.120.27.188, announced in 34.120.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. schweizerlust.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 · schweizerlust.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/schweizerlust.com

Resolution chain

IPv6 resolution

No AAAA record for schweizerlust.com is recorded in WhisperGraph.

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
digibyte media b.v.
Contact emails
b5b0ecdbcc@schweizerlust.com.whoistrustee.com, info@domain-contact.org, 4743db74869708eb301876729146446d90a8a7749416fb4f338ceb08fb6bb1a9@schweizerlust.com.whoisproxy.org, 4a82113bc8905b1a4147492990ebe19f81091bffd96072c43dfe81beafb5ae00@schweizerlust.com.whoisproxy.org, 6479f5e3d5d7cb42a81bad3579b5fcac0cbe594304ddfd81aa1644a70d3e2dd6@schweizerlust.com.whoisproxy.org, ef8d91f52b40c92ad21ec5789407957e8fc39b5845c328ad3ef26b611c64d5f3@schweizerlust.com.whoisproxy.org

Subdomains

Subdomain
acc.schweizerlust.com
admin.schweizerlust.com
ajax.schweizerlust.com
api.schweizerlust.com
forward.schweizerlust.com
hostmaster.schweizerlust.com
json.schweizerlust.com
link.schweizerlust.com
www.schweizerlust.com

Showing 9 of 12. View all subdomains →

Mail and authentication

Nameservers

  • ns1.dnsimple.com
  • ns3.dnsimple.com
  • ns1.dnsimple-edge.com
  • ns3.dnsimple-edge.io
  • ns2.dnsimple-edge.net
  • ns4.dnsimple-edge.org

MX records

  • mx1.earfulwolf.com

SPF policy

  • include: spf.earfulwolf.com
  • include: 136224628.spf2.netcorecloud.net

Threat-feed evidence

History

Related pages

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