Skip to content

Hostname

truecalendar.com

Last fetched

truecalendar.com resolves to 13.227.192.101, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. truecalendar.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 · truecalendar.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/truecalendar.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of truecalendar.com owner
Contact emails
vi_sk@yahoo.com, 1af37d78-e129-4228-8a70-22903b539bac@identity-protect.org, 341b5552-ed12-46db-8ea1-a2115d790925@identity-protect.org, 3ed5730d-ed98-41d6-90d1-cfff39cd7abe@identity-protect.org, c514c226-ef97-489d-96ab-198c82e02124@identity-protect.org, cf8b9046-b657-44b1-a351-8fc976930bb8@identity-protect.org, fa6425cb-3a4c-49fc-8d5b-7a8618a5b379@identity-protect.org, owner-2749479@truecalendar.com.whoisprivacyservice.org

Subdomains

Subdomain
stag.truecalendar.com
staging.truecalendar.com
wildcard.truecalendar.com
www.truecalendar.com

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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-155.awsdns-19.com
  • ns-569.awsdns-07.net
  • ns-1135.awsdns-13.org
  • ns-1814.awsdns-34.co.uk

MX records

  • mx01.mail.icloud.com
  • mx02.mail.icloud.com

SPF policy

  • include: amazonses.com
  • include: icloud.com

Threat-feed evidence

History

Related pages

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