Skip to content

Hostname

glamira.de

Last fetched

glamira.de resolves to 3.127.60.101, announced in 3.124.0.0/14 by AMAZON-02 - Amazon.com, Inc. in DE. glamira.de 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 · glamira.deRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/glamira.de

Resolution chain

IPv6 resolution

No AAAA record for glamira.de is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for glamira.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
admin.glamira.de
backoffice-server.glamira.de
backoffice-test.glamira.de
backoffice.glamira.de
blog.glamira.de
chat-dashboard-backend.glamira.de
dev.glamira.de
dev1.glamira.de
dev2.glamira.de
dev3.glamira.de
dev5.glamira.de
freshdesk-app-backend.glamira.de

Showing 12 of 34. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-111.awsdns-13.com
  • ns-828.awsdns-39.net
  • ns-1095.awsdns-08.org
  • ns-1957.awsdns-52.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: email.freshdesk.com

Threat-feed evidence

History

Related pages

Pivot from glamira.de 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: "glamira.de"})-[: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.