Skip to main content

Security report for numverify.com

Numverify · Technology · N/a

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

0–100, higher is better. How it is calculated

Numverify is a specialized technology company providing a JSON API service focused on international and national phone number validation, carrier, location, and line type lookup. The company targets developers and businesses requiring reliable phone number verification services. Their market position is that of a niche API provider with a subscription-based business model, founded in 2015. The website content is professional, well-structured, and designed to facilitate developer engagement and service adoption. Technically, the website employs a modern tech stack including jQuery, Google Tag Manager, Facebook SDK, and Cloudflare DNS services. The site is hosted on infrastructure registered via GoDaddy and uses Cloudflare for DNS, although DNSSEC is not enabled. Performance and mobile optimization are good, with basic accessibility features and solid SEO practices. From a security perspective, the site enforces HTTPS and uses domain status locks to prevent unauthorized domain changes. However, it lacks DNSSEC and a published security.txt file, and does not explicitly disclose incident response policies or security frameworks. Tracking and marketing tools are used responsibly with privacy policies and cookie consent mechanisms in place. Overall, Numverify presents a trustworthy and professional online presence with a good security posture and compliance awareness. Strategic improvements in DNS security and incident response transparency would further enhance their security maturity and trustworthiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

4 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching numverify.com

This scan found 22 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
65
Security headers
35
Email security
60
DNS health
80
Network security
100
GDPR outside view
68
Average
68

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Numverify operates in the technology sector, offering API services for phone number validation and lookup. Their business model is subscription and usage-based, targeting developers and enterprises needing phone verification. The company has maintained consistent domain registration since 2015, indicating stable operations. Their marketing ecosystem includes partnerships with major platforms like Facebook and Google for advertising and analytics. The website content and branding are consistent, supporting a clear market positioning as a reliable API provider. No parent or subsidiary companies are identified, suggesting an independent operation. The company leverages modern web technologies and maintains good privacy and terms of service documentation, supporting customer trust and regulatory compliance.

Security posture

The security posture of Numverify is solid with HTTPS enforced and domain status protections in place. The absence of DNSSEC is a minor gap that could be addressed to improve DNS security. No critical vulnerabilities or exposed sensitive data were detected in the website content or scripts. The site uses common third-party scripts including Google Tag Manager and Facebook SDK, which are industry standard but require ongoing monitoring for vulnerabilities. Privacy policies and cookie consent mechanisms indicate compliance with GDPR and related regulations. However, the lack of a published security policy, incident response contact, or vulnerability disclosure program limits transparency and readiness. Overall, the site demonstrates good security hygiene but could benefit from enhanced security documentation and DNS security improvements.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a security.txt file to provide clear vulnerability disclosure and incident response contacts.
  3. Add explicit security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Disclose incident response policies and provide dedicated security contact emails (e.g., security@numverify.com).
  5. Regularly audit and update third-party scripts to mitigate risks from external dependencies.

Contact details published on the site

Addresses
Legal name
Numverify
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Numverify
Description
Numverify API is a powerful JSON API providing international and national phone number validation, carrier, location, and line type lookup for developers.
Key services
phone number validation, carrier lookup, location lookup, line type lookup
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.11.1, Google Tag Manager, Facebook SDK, Cloudflare DNS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Domain status includes clientDeleteProhibited etc. to prevent unauthorized changes

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Reddit Ads, Google Ads
Tracking pixels
Facebook Pixel
Marketing tools
Facebook SDK
Transparency
good

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website provides a specialized API service for phone number validation and lookup
  2. Content is professional and targeted at developers and businesses
  3. Uses modern tracking and marketing tools with privacy policies in place
  4. No signs of malicious or suspicious activity
  5. Security posture is good but could be improved with DNSSEC and security.txt
Technical notes

Notes

The website uses a custom or unknown CMS with a tech stack including jQuery 1.11.1, Google Tag Manager, and Facebook SDK. Hosting is managed via GoDaddy for domain registration and Cloudflare for DNS services. Performance is moderate with good mobile optimization and basic accessibility features. SEO is well implemented with proper meta tags and canonical links. The site uses multiple analytics and marketing tools, indicating a mature digital marketing strategy. There is some technical debt indicated by the use of an older jQuery version (1.11.1). Modernization opportunities include updating JavaScript libraries and enhancing security headers. Overall, the technical infrastructure supports the business needs effectively with room for incremental improvements.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with numverify.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review numverify.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.