Hostname
wow.show
Last fetched
wow.show resolves to 18.153.202.115, announced in 18.153.0.0/16 by AMAZON-02 - Amazon.com, Inc. in DE. wow.show is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 18.153.202.115
18.153.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.156.27.251
18.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.195.227.195
18.194.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.198.0.158
18.198.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.123.223.109
3.120.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.123.96.136
3.120.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.124.128.54
3.124.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.126.150.133
3.124.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.66.250.58
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.74.211.14
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.74.56.159
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 35.156.170.67
35.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 35.156.50.175
35.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.57.206.241
52.57.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.58.194.115
52.58.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 54.93.147.243
54.93.128.0/17 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.176.248.93
63.176.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for wow.show is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Company
- Company
- WOW
Technology
WOW has been observed using 18 technologies somewhere in its estate. This is observed use, not an exposure finding.
- Open Graph · content management system
- Google Analytics · intelligence and analytics
- JSON-LD · frameworks and libraries
- HSTS · security
- X-Content-Type-Options · web & portal technology
- Google Tag Manager · tag management
- Google Search Console · performance
- Amazon Web Services · cloud hosting
- Facebook · social media analytics and monitoring
- Microsoft 365 · email
- Facebook Pixel · analytics
- Office 365 · communication and collaboration
- Amazon ALB · load balancers
- Vue.js · javascript frameworks
- Amazon Route 53 · domain name services
- TikTok Pixel · analytics
- Mautic · content management system
- AWS Elastic Load Balancer · it infrastructure
Subdomains
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for wow.show.
DKIM signing
No DKIM signing vendor is attributed to wow.show in WhisperGraph.
Nameservers
- ns-226.awsdns-28.com
- ns-870.awsdns-44.net
- ns-1476.awsdns-56.org
- ns-2019.awsdns-60.co.uk
MX records
- wow-show.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from wow.show into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.