Skip to content

Hostname

looppay.com

Last fetched

looppay.com resolves to 13.226.155.103, announced in 13.226.152.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. looppay.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 · looppay.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/looppay.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of looppay.com owner
Contact emails
domainsmanager@looppay.com, 13b73adc-8496-4259-9ac7-1622c1a5ef41@identity-protect.org, 4c7183cc-dd01-4f8f-be1b-1dca351a7adc@identity-protect.org, 6684f3b9-5221-4656-b030-f3ebc01bea49@identity-protect.org, 8620290f-3d6b-4e7e-9147-b2c4110c0e75@identity-protect.org, 8e7826dc-7dba-4e1c-b777-b924522126cc@identity-protect.org, c0278706-3eee-4f1f-8d13-9a009ff77ed0@identity-protect.org, owner-11681576@looppay.com.whoisprivacyservice.org, owner-3386835@looppay.com.whoisprivacyservice.org, owner-7886881@looppay.com.whoisprivacyservice.org

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-125.awsdns-15.com
  • ns-191.awsdns-23.com
  • ns-586.awsdns-09.net
  • ns-795.awsdns-35.net
  • ns-1052.awsdns-03.org
  • ns-1325.awsdns-37.org
  • ns-1927.awsdns-48.co.uk
  • ns-1991.awsdns-56.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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