Skip to content

Hostname

tmrs.com

Last fetched

tmrs.com resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.

Nutrition Label

WHISPER CANON · tmrs.comRouting diversityPeering densityMOAS conflictThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/host/tmrs.com

Resolution chain

tmrs.com resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
18.173.132.5418.173.132.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
18.173.132.6118.173.132.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
18.173.132.6618.173.132.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
18.173.132.818.173.132.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
3.161.82.1163.161.80.0/22AS16509AMAZON-02 - Amazon.com, Inc.DE
3.161.82.1273.161.80.0/22AS16509AMAZON-02 - Amazon.com, Inc.DE
3.161.82.373.161.80.0/22AS16509AMAZON-02 - Amazon.com, Inc.DE
3.161.82.893.161.80.0/22AS16509AMAZON-02 - Amazon.com, Inc.DE
3.167.246.123.167.240.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
3.167.246.273.167.240.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
3.167.246.293.167.240.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
3.167.246.783.167.240.0/21AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

Registrar
iana:468
Organization
on behalf of tmrs.com owner
Contact emails

Subdomains

18 observed subdomains of tmrs.com.

Web-graph footprint

Distinct hostnames that link to or from tmrs.com in the public web crawl.

Threat posture

History

Mail and authentication

SPF policy

9 SPF mechanisms authorising senders for tmrs.com.

MechanismTarget
SPF_INCLUDEclientspf.backstopsolutions.com
SPF_INCLUDEem9785.tmrs.com
SPF_INCLUDEsent-via.netsuite.com
SPF_INCLUDEspf.protection.outlook.com
SPF_INCLUDEu24013496.wl247.sendgrid.net
SPF_INCLUDEus._netblocks.mimecast.com
SPF_IP159.183.153.219
SPF_IP216.166.2.18
SPF_MXtmrs.com

Related pages

Pivot deeper into the graph from tmrs.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "tmrs.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.