Skip to content

Hostname

ling-app.com

Last fetched

ling-app.com resolves to 104.21.27.217, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ling-app.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 · ling-app.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/ling-app.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1479
Registrant organisation
domain administrator
Contact emails
pw-321bc5096fc108fa010d629c80bde50a@privacyguardian.org, pw-845116d1fb0281c54f97b6022b84897c@privacyguardian.org, pw-c6c279bcb85ef3110e3cbbb895d79318@privacyguardian.org, pw-eda83ec744542e23f8eda2078a63ff7f@privacyguardian.org

Subdomains

Subdomain
ai-tutor.ling-app.com
alert.ling-app.com
app.ling-app.com
china.ling-app.com
get.ling-app.com
hello.ling-app.com
help.ling-app.com
live.ling-app.com
mail.ling-app.com
play.ling-app.com
prod.ling-app.com
support.ling-app.com

Showing 12 of 20. 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

Mail and authentication

Nameservers

  • alex.ns.cloudflare.com
  • liv.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • mx3.zoho.com

SPF policy

  • include: _spf.google.com
  • include: _spf.postaffiliatepro.com
  • include: zoho.com
  • include: spf.zoho.com
  • include: 47358698.spf08.hubspotemail.net
  • include: transmail.net
  • include: zcsend.net

Threat-feed evidence

History

Related pages

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