Hostname
faircare.de
Last fetched
faircare.de resolves to 13.227.192.115, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. faircare.de 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
- 13.227.192.115
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.49
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.78
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.81
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.35.58.112
13.35.58.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.35.58.12
13.35.58.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.35.58.43
13.35.58.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.35.58.55
13.35.58.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.184.245.249
18.184.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.104
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.123
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.21
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.71
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 35.157.243.99
35.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for faircare.de is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for faircare.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
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
- ns-353.awsdns-44.com
- ns-656.awsdns-18.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1151.awsdns-15.org
- ns-1573.awsdns-04.co.uk
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
SPF policy
- include: _spf.google.com
- include: mail.zendesk.com
Threat-feed evidence
History
Related pages
Pivot from faircare.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: "faircare.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.