Skip to content

Hostname

trueaccord.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
domains by proxy,
Contact emails
admin@trueaccord.com, trueaccord.com@domainsbyproxy.com, support@trueaccord.com, 84300cf0165bd28f7d85f0005d7c35d8-5846094@contact.gandi.net

Subdomains

Subdomain
_spf-internal.trueaccord.com
api.trueaccord.com
app.trueaccord.com
blog.trueaccord.com
consumers.trueaccord.com
corp.trueaccord.com
demo.trueaccord.com
dev.trueaccord.com
dlp.trueaccord.com
docs.trueaccord.com
email.trueaccord.com
eng.trueaccord.com

Showing 12 of 111. 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-90.awsdns-11.com
  • ns-956.awsdns-55.net
  • ns-1161.awsdns-17.org
  • ns-1804.awsdns-33.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: _spf.google.com
  • include: _spf.psm.knowbe4.com
  • include: _spf.salesforce.com
  • include: _spf-internal.trueaccord.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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